Implementing service lines

Before you begin setting up service lines, you need to decide how you want to add, manage, and process them. You can choose one of the following options:

  • Axiom rule-based service lines - You add, manage, and process schemas and definitions all within Axiom, which runs each encounter through a series of filters to determine what encounters to assign to a service line. You can create up to eight service line schemas that include an unlimited number of service line definitions. You order the definitions the way you want the system to evaluate each encounter. Each night, the system automatically processes and tags each encounter using a job in Axiom Scheduler. You can also activate or deactivate definitions, as needed. For example, let's say you want to add a new service line at the beginning of the fiscal year. You can add the new service line definition at any time but keep it inactive until you are ready to use it.
  • Client imported service lines - If your organization uses a third-party application to define service lines—such as Sg2, Truven Health Analytics, or even your own host system—you can import them directly into Axiom without needing to create an entire set of service line rules from scratch. This allows you to continue managing and processing service lines outside the Axiom system, and simply import them with the help of a job in Axiom Scheduler.

NOTE: Once you choose a method on how to manage and process schemas, you should continue to use that method. Do not mix methods.

Importing third-party service lines

This section walks you through the best practice for importing third-party service lines into Axiom. You should first familiarize yourself with Axiom's import and scheduling capabilities before completing these steps. For more information, see Importing data and Scheduler.

TIP: During the implementation process, your Syntellis Implementation Consultant can help you complete these steps. If you need help after implementation, create a support case with Syntellis Support.

To import service lines:

  1. In the Service Line Schemas utility, create the schemas and service lines to be imported.

  2. Create an import Create an import to map the data from your raw data file that includes the encounters and service lines to the \Axiom\Table Library\DSS\Service Line Builder\Enc_ServiceLineStaging table. For instructions on creating an import, see "Importing external source data" in the online help.

    NOTE: Only users assigned both the DSS Admin and the CostDSS Import Admin role profiles can complete steps 2 and 3 in this procedure.

  3. Create a Scheduler job Create a Scheduler job to run the \Axiom\Imports Library\DSS\Import Enc_Serviceline from staging import to move the data from the Enc_ServiceLineStaging table to the Enc_ServiceLine table. For instructions, see "Scheduler job setup" in the online help.

If the service lines happen to be imported before creating them in Axiom (as described in step 1 above), the system will still create the schemas for you. Axiom makes these easy to identify by displaying them as *****Schema Created From Client Import***** in the Service Line Schemas utility. You will simply need to update the schema or service line definition by doing the following:

  • Update the name.

    IMPORTANT: Use caution when changing the name since it maps to the schema or service line with the same name in the imported file. If you change the name, you will also need to change it in the mapping of the imported file so that the data loads correctly.

  • Enter a description of the schema or service line.
  • Activate the schema or service line when ready to push data to Axiom Intelligence for reporting (schemas or service lines imported in this way are automatically set to inactive).
  • Identify a schema as the main reporting schema used for Axiom Intelligence reports, if applicable.
  • The encounter filters do not display in the service line definitions nor can you process schemas because it is assumed that encounters have already been processed and tagged outside the Axiom system. Importing just provides a way to get this information into the Axiom database for reporting purposes.